Experimental WinPowerShell DSC import extension #1025
Conversation
Gijsreyn
changed the title
|
@SteveL-MSFT Any idea why the Windows build failed on fetching packages? |
|
@Gijsreyn I'd hold off on this for now, I'm working on a big PR to fix the Windows CI. Basically there was one issue in a test which caused Pester to crash so even though Windows tests have been failing, it was never reported. Since making that fix, many existing tests are failing which I'm now fixing one by one. |
…into implement-powershell-import-extension
Gijsreyn
force-pushed
the
implement-powershell-import-extension
branch
from
a9e618e to
5fdc34d
Compare
…b.com/Gijsreyn/operation-methods into implement-powershell-import-extension
|
Hi @SteveL-MSFT, this one was a pretty tough one, especially with the latest fixes on the Now there's a conflict between the ones. Is there another indication to tell DSC's engine what extension to use? |
SteveL-MSFT
requested review from
theJasonHelmick,
michaeltlombardi and
mgreenegit
Gijsreyn
force-pushed
the
implement-powershell-import-extension
branch
from
6bdf559 to
f7069cb
Compare
PR Summary
This PR introduces a Windows PowerShell DSC import extension that enables the passing in of PSDSC v2 configuration documents.
PR Context
The PR adds three new files to the build:
convert-resource.ps1convertDscResource.psd1convertDscResource.psm1When a user passes in a
.ps1file with a valid DSC configuration document, an attempt is made to convert it by borrowing content from DSCParser.